Skip to content

govulncheck: use golang:1.24 as a base image#166

Merged
xcoulon merged 2 commits intocodeready-toolchain:masterfrom
xcoulon:govulncheck_go_1_24
Jan 30, 2026
Merged

govulncheck: use golang:1.24 as a base image#166
xcoulon merged 2 commits intocodeready-toolchain:masterfrom
xcoulon:govulncheck_go_1_24

Conversation

@xcoulon
Copy link
Contributor

@xcoulon xcoulon commented Jan 30, 2026

all active repositories have migrated to Go 1.24

also, local build is now called govulncheckx to distinguish from the official govulncheck

Signed-off-by: Xavier Coulon xcoulon@redhat.com

Summary by CodeRabbit

  • Chores
    • Binary renamed from govulncheck to govulncheckx
    • Go toolchain updated to version 1.24.0

✏️ Tip: You can customize this high-level summary in your review settings.

all active repositories have migrated to Go 1.24

also, local build is now called `govulncheckx` to distinguish from the official `govulncheck`

Signed-off-by: Xavier Coulon <xcoulon@redhat.com>
@coderabbitai
Copy link

coderabbitai bot commented Jan 30, 2026

Walkthrough

The PR updates the Go base image in the Containerfile from 1.23.0 to 1.24.0 and simplifies the makefile by renaming the binary output to govulncheckx while removing git commit and build timestamp tracking logic.

Changes

Cohort / File(s) Summary
Containerfile Update
govulncheck-action/Containerfile
Updated base image from golang:1.23.0 to golang:1.24.0.
Build Configuration
govulncheck-action/makefile
Renamed binary output from govulncheck to govulncheckx in build and install targets; removed GIT_COMMIT_ID_SHORT and BUILD_TIME variable calculations.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~5 minutes

Possibly related PRs

Suggested reviewers

  • MatousJobanek
  • alexeykazakov
  • mfrancisc

Poem

🐰 A newer Go arrives today,
Hopping versions out of way,
Binary renamed with style so grand,
Simpler builds across the land,
Our toolchain hops to tomorrow's way!

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately describes the primary change: updating the Dockerfile base image from golang:1.23.0 to golang:1.24.0.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)
govulncheck-action/Containerfile (1)

15-19: ⚠️ Potential issue | 🔴 Critical

Change the base image tag from golang:1.24.0 to golang:1.24.12 (or golang:1.24)—the 1.24.0 tag does not exist.

The golang:1.24.0 tag is not available on Docker Hub; as of January 2026, the latest patch in the 1.24 line is 1.24.12. This will cause the Docker build to fail when pulling the base image. Use golang:1.24.12 or the floating tag golang:1.24 instead.

Also update the stale comment on line 18 that references Go 1.23.0:

Suggested fix
-FROM golang:1.24.0
+FROM golang:1.24.12
 # using a fresh golang image without the `WORKDIR` from the builder stage
 # see https://docs.github.com/en/actions/reference/workflows-and-actions/dockerfile-support#workdir
-# using golang 1.23.0 since most of our projects are still using it (and toolchain will not downgrade the version of go)
+# using golang 1.24.12 since most of our projects are now using it (and toolchain will not downgrade the version of Go)

@xcoulon
Copy link
Contributor Author

xcoulon commented Jan 30, 2026

Actionable comments posted: 0

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

govulncheck-action/Containerfile (1)> 15-19: ⚠️ Potential issue | 🔴 Critical

Change the base image tag from golang:1.24.0 to golang:1.24.12 (or golang:1.24)—the 1.24.0 tag does not exist.
The golang:1.24.0 tag is not available on Docker Hub; as of January 2026, the latest patch in the 1.24 line is 1.24.12. This will cause the Docker build to fail when pulling the base image. Use golang:1.24.12 or the floating tag golang:1.24 instead.
Also update the stale comment on line 18 that references Go 1.23.0:

Suggested fix

-FROM golang:1.24.0
+FROM golang:1.24.12
 # using a fresh golang image without the `WORKDIR` from the builder stage
 # see https://docs.github.com/en/actions/reference/workflows-and-actions/dockerfile-support#workdir
-# using golang 1.23.0 since most of our projects are still using it (and toolchain will not downgrade the version of go)
+# using golang 1.24.12 since most of our projects are now using it (and toolchain will not downgrade the version of Go)

the 1.24.0 tag exists:

$ skopeo list-tags docker://golang | grep '1.24.0'
        "1.24.0",
        "1.24.0-alpine",
        "1.24.0-alpine3.20",
        "1.24.0-alpine3.21",
        "1.24.0-bookworm",
        "1.24.0-bullseye",
        "1.24.0-nanoserver",
        "1.24.0-nanoserver-1809",
        "1.24.0-nanoserver-ltsc2022",
        "1.24.0-nanoserver-ltsc2025",
        "1.24.0-windowsservercore",
        "1.24.0-windowsservercore-1809",
        "1.24.0-windowsservercore-ltsc2022",
        "1.24.0-windowsservercore-ltsc2025",

@xcoulon xcoulon merged commit d7a00e6 into codeready-toolchain:master Jan 30, 2026
3 checks passed
@xcoulon xcoulon deleted the govulncheck_go_1_24 branch January 30, 2026 13:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants